If you’re as clever as you can be when you write it, how will you ever debug it?

As we said in the preface to the first edition, C “wears well as one’s experience with it grows.” With a decade more experience, we still feel that way.

Get the weirdnesses into the data where you can manipulate them easily, and the regularity into the code because regular code is a lot easier to work with.

An effective way to test code is to exercise it at its natural boundaries.

Believe the terrain, not the map.

Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won’t do it well anyway.

Don’t document bad code – rewrite it.

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.

Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won't do it well anyway.

Controlling complexity is the essence of computer programming.